Data detection

ABSTRACT

In some embodiments, a device determines a current context of a plurality of terms, in accordance with a determination that the current context is a first context, selects one or more terms in the plurality of terms based on a first word list as actionable terms, and in accordance with a determination that the current context is a second context, different from the first context, selects one or more terms in the plurality of terms as actionable terms based on a second word list, different from the first word list. In some embodiments, the device displays the plurality of terms, wherein one or more of the actionable terms are visually distinguished from other terms. In some embodiments, a device obtains related content associated with the actionable terms, and after obtaining the related content, concurrently displays a representation of the related content along with the plurality of terms.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 14/657,019, filed Mar. 13, 2015 and published on Jun. 2, 2016 as U.S. Patent Publication No. 2016/0154544, which claims the benefit of U.S. Provisional Application No. 62/086,610 filed on Dec. 2, 2014, the entire disclosures of which are herein incorporated by reference in their entirety for all purposes.

FIELD OF THE DISCLOSURE

This relates generally to electronic devices that detect relevant data in communications.

BACKGROUND OF THE DISCLOSURE

Communication between people using electronic devices has increased significantly in recent years. These devices can be devices such as computers, tablet computers, televisions, multimedia devices, mobile devices, and the like.

These communications often consist of user-provided content (e.g., text, images, etc.) being transmitted from one electronic device to another. Enhancing these communications improves the user's experience with the device and decreases user interaction time, which is particularly important where input devices are battery-operated.

SUMMARY OF THE DISCLOSURE

The embodiments described in this disclosure are directed to one or more devices that optionally select terms in communications as actionable terms based on context-dependent word lists, and automatically populate the communications with content related to the communications, and one or more actions related to the above that the devices optionally perform. The full descriptions of the embodiments are provided in the Drawings and the Detailed Description, and it is understood that the Summary provided above does not limit the scope of the disclosure in any way.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments, reference should be made to the Detailed Description below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a multifunction device with a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for event handling in accordance with some embodiments.

FIG. 2 illustrates a multifunction device having a touch screen in accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.

FIG. 4 illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display in accordance with some embodiments.

FIGS. 5A-5O illustrate exemplary ways in which electronic devices select terms in communications between users based on a context of the terms in accordance with some embodiments of the disclosure.

FIGS. 6A-6E are flow diagrams illustrating a method of selecting terms in communications between users based on a context of the terms in accordance with some embodiments.

FIGS. 7A-7F illustrate exemplary ways in which an electronic device automatically populates a user interface with content in accordance with some embodiments of the disclosure.

FIGS. 8A-8C are flow diagrams illustrating a method of automatically populating a user interface with content in accordance with some embodiments.

FIGS. 9-10 are functional block diagrams of electronic devices in accordance with some embodiments.

DETAILED DESCRIPTION

In the following description of embodiments, reference is made to the accompanying drawings which form a part hereof, and in which it is shown by way of illustration specific embodiments that are optionally practiced. It is to be understood that other embodiments are optionally used and structural changes are optionally made without departing from the scope of the disclosed embodiments.

Exemplary Devices

Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touch pads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer or a television with a touch-sensitive surface (e.g., a touch screen display and/or a touch pad). In some embodiments, the device does not have a touch screen display and/or a touch pad, but rather is capable of outputting display information (such as the user interfaces of the disclosure) for display on a separate display device, and capable of receiving input information from a separate input device having one or more input mechanisms (such as one or more buttons, a touch screen display and/or a touch pad). In some embodiments, the device has a display, but is capable of receiving input information from a separate input device having one or more input mechanisms (such as one or more buttons, a touch screen display and/or a touch pad).

In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse and/or a joystick. Further, as described above, it should be understood that the described electronic device, display and touch-sensitive surface are optionally distributed amongst two or more devices. Therefore, as used in this disclosure, information displayed on the electronic device or by the electronic device is optionally used to describe information outputted by the electronic device for display on a separate display device (touch-sensitive or not). Similarly, as used in this disclosure, input received on the electronic device (e.g., touch input received on a touch-sensitive surface of the electronic device) is optionally used to describe input received on a separate input device, from which the electronic device receives input information.

The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, a television channel browsing application, and/or a digital video player application.

The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable or non-portable devices with touch-sensitive displays, though the devices need not include touch-sensitive displays or displays in general, as described above. FIG. 1A is a block diagram illustrating portable or non-portable multifunction device 100 with touch-sensitive displays 112 in accordance with some embodiments. Touch-sensitive display 112 is sometimes called a “touch screen” for convenience, and is sometimes known as or called a touch-sensitive display system. Device 100 includes memory 102 (which optionally includes one or more computer readable storage mediums), memory controller 122, one or more processing units (CPU's) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem 106, other input or control devices 116, and external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more intensity sensors 165 for detecting intensity of contacts on device 100 (e.g., a touch-sensitive surface such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile outputs on device 100 (e.g., generating tactile outputs on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate over one or more communication buses or signal lines 103.

As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure).

As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.

It should be appreciated that device 100 is only one example of a portable or non-portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in FIG. 1A are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and/or application specific integrated circuits. Further, the various components shown in FIG. 1A are optionally implemented across two or more devices; for example, a display and audio circuitry on a display device, a touch-sensitive surface on an input device, and remaining components on device 100. In such an embodiment, device 100 optionally communicates with the display device and/or the input device to facilitate operation of the system, as described in the disclosure, and the various components described herein that relate to display and/or input remain in device 100, or are optionally included in the display and/or input device, as appropriate.

Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by other components of device 100, such as CPU 120 and the peripherals interface 118, is, optionally, controlled by memory controller 122.

Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data.

In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The wireless communication optionally uses any of a plurality of communications standards, protocols and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212, FIG. 2). The headset jack provides an interface between audio circuitry 110 and removable audio input/output peripherals, such as output-only headphones or a headset with both output (e.g., a headphone for one or both ears) and input (e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161 and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input or control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, infrared port, USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208, FIG. 2) optionally include an up/down button for volume control of speaker 111 and/or microphone 113. The one or more buttons optionally include a push button (e.g., 206, FIG. 2).

Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. As described above, the touch-sensitive operation and the display operation of touch-sensitive display 112 are optionally separated from each other, such that a display device is used for display purposes and a touch-sensitive surface (whether display or not) is used for input detection purposes, and the described components and functions are modified accordingly. However, for simplicity, the following description is provided with reference to a touch-sensitive display. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, Calif.

Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable or non-portable devices.

Device 100 optionally also includes one or more optical sensors 164. FIG. 1A shows an optical sensor coupled to optical sensor controller 158 in I/O subsystem 106. Optical sensor 164 optionally includes charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Optical sensor 164 receives light from the environment, projected through one or more lens, and converts the light to data representing an image. In conjunction with imaging module 143 (also called a camera module), optical sensor 164 optionally captures still images or video. In some embodiments, an optical sensor is located on the back of device 100, opposite touch screen display 112 on the front of the device, so that the touch screen display is enabled for use as a viewfinder for still and/or video image acquisition. In some embodiments, another optical sensor is located on the front of the device so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conference participants on the touch screen display.

Device 100 optionally also includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I/O subsystem 106. Contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor 165 receives contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touch screen display 112 which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166. FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternately, proximity sensor 166 is coupled to input controller 160 in I/O subsystem 106. In some embodiments, the proximity sensor turns off and disables touch screen 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile output generators 167. FIG. 1A shows a tactile output generator coupled to haptic feedback controller 161 in I/O subsystem 106. Tactile output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components and/or electromechanical devices that convert energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts electrical signals into tactile outputs on the device). Contact intensity sensor 165 receives tactile feedback generation instructions from haptic feedback module 133 and generates tactile outputs on device 100 that are capable of being sensed by a user of device 100. In some embodiments, at least one tactile output generator is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system 112) and, optionally, generates a tactile output by moving the touch-sensitive surface vertically (e.g., in/out of a surface of device 100) or laterally (e.g., back and forth in the same plane as a surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touch screen display 112 which is located on the front of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG. 1A shows accelerometer 168 coupled to peripherals interface 118. Alternately, accelerometer 168 is, optionally, coupled to an input controller 160 in I/O subsystem 106. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers. Device 100 optionally includes, in addition to accelerometer(s) 168, a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information concerning the location and orientation (e.g., portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments memory 102 stores device/global internal state 157, as shown in FIGS. 1A and 3. Device/global internal state 157 includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch screen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and location information concerning the device's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.

Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with the 30-pin connector used on iPod (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact) determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.

In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined thresholds values without changing the trackpad or touch screen display hardware. Additionally, in some implementations a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).

Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns and intensities. Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (lift off) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (lift off) event.

Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including without limitation text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations and the like.

In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).

GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing, to camera 143 as picture/video metadata, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact         list);     -   telephone module 138;     -   video conferencing module 139;     -   e-mail client module 140;     -   instant messaging (IM) module 141;     -   workout support module 142;     -   camera module 143 for still and/or video images;     -   image management module 144;     -   browser module 147;     -   calendar module 148;     -   widget modules 149, which optionally include one or more of:         weather widget 149-1, stocks widget 149-2, calculator widget         149-3, alarm clock widget 149-4, dictionary widget 149-5, and         other widgets obtained by the user, as well as user-created         widgets 149-6;     -   widget creator module 150 for making user-created widgets 149-6;     -   search module 151;     -   video and music player module 152, which is, optionally, made up         of a video player module and a music player module;     -   notes module 153;     -   map module 154;     -   online video module 155.

Examples of other applications 136 that are, optionally, stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, contacts module 137 are, optionally, used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, telephone module 138 are, optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in address book 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, videoconferencing module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in a MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module 146, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store and transmit workout data.

In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to do lists, etc.) in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 are, optionally, used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).

In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to do lists, and the like in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 are, optionally, used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions; data on stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video.

Each of the above identified modules and applications correspond to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are, optionally, combined or otherwise re-arranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 102 optionally stores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad (whether included in device 100 or on a separate device, such as an input device). By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In some embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. In some embodiments, memory 102 (in FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., in operating system 126) and a respective application 136-1 (e.g., any of the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.

Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripheral interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.

Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views, when touch-sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.

Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.

Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver module 182.

In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177 or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 includes one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170, and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.

Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event 187 include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first lift-off (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second lift-off (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and lift-off of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event 187 also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module 145. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 176 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays and/or touchpads also applies to other forms of user inputs to operate multifunction devices 100 with input-devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.

FIG. 2 illustrates a portable or non-portable multifunction device 100 having a touch screen 112 in accordance with some embodiments. As stated above, multifunction device 100 is described as having the various illustrated structures (such as touch screen 112, speaker 111, accelerometer 168, microphone 113, etc.); however, it is understood that these structures optionally reside on separate devices. For example, display-related structures (e.g., display, speaker, etc.) and/or functions optionally reside on a separate display device, input-related structures (e.g., touch-sensitive surface, microphone, accelerometer, etc.) and/or functions optionally reside on a separate input device, and remaining structures and/or functions optionally reside on multifunction device 100.

The touch screen 112 optionally displays one or more graphics within user interface (UI) 200. In this embodiment, as well as others described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and/or downward) and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with device 100. In some implementations or circumstances, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

Device 100 optionally also includes one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.

In one embodiment, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, Subscriber Identity Module (SIM) card slot 210, head set jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. Device 300 need not include the display and the touch-sensitive surface, as described above, but rather, in some embodiments, optionally communicates with the display and the touch-sensitive surface on other devices. Additionally, device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device (such as a television or a set-top box), a navigation device, an educational device (such as a child's learning toy), a gaming system, or a control device (e.g., a home or industrial controller). Device 300 typically includes one or more processing units (CPU's) 310, one or more network or other communications interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. Communication buses 320 optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Device 300 includes input/output (I/O) interface 330 comprising display 340, which is typically a touch screen display. I/O interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and touchpad 355, tactile output generator 357 for generating tactile outputs on device 300 (e.g., similar to tactile output generator(s) 167 described above with reference to FIG. 1A), sensors 359 (e.g., optical, acceleration, proximity, touch-sensitive, and/or contact intensity sensors similar to contact intensity sensor(s) 165 described above with reference to FIG. 1A). Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 370 optionally includes one or more storage devices remotely located from CPU(s) 310. In some embodiments, memory 370 stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in memory 102 of portable or non-portable multifunction device 100 (FIG. 1A), or a subset thereof. Furthermore, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable or non-portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, word processing module 384, website creation module 386, disk authoring module 388, and/or spreadsheet module 390, while memory 102 of portable or non-portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

Each of the above identified elements in FIG. 3 are, optionally, stored in one or more of the previously mentioned memory devices. Each of the above identified modules corresponds to a set of instructions for performing a function described above. The above identified modules or programs (e.g., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are, optionally, combined or otherwise re-arranged in various embodiments. In some embodiments, memory 370 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 370 optionally stores additional modules and data structures not described above.

FIG. 4 illustrates an exemplary user interface on a device (e.g., device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet or touchpad 355, FIG. 3) that is separate from the display 450 (e.g., touch screen display 112). Device 300 also, optionally, includes one or more contact intensity sensors (e.g., one or more of sensors 357) for detecting intensity of contacts on touch-sensitive surface 451 and/or one or more tactile output generators 359 for generating tactile outputs for a user of device 300.

Although some of the examples which follow will be given with reference to inputs on touch screen display 112 (where the touch sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in FIG. 4. In some embodiments the touch sensitive surface (e.g., 451 in FIG. 4) has a primary axis (e.g., 452 in FIG. 4) that corresponds to a primary axis (e.g., 453 in FIG. 4) on the display (e.g., 450). In accordance with these embodiments, the device detects contacts (e.g., 460 and 462 in FIG. 4) with the touch-sensitive surface 451 at locations that correspond to respective locations on the display (e.g., in FIG. 4, 460 corresponds to 468 and 462 corresponds to 470). In this way, user inputs (e.g., contacts 460 and 462, and movements thereof) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4) are used by the device to manipulate the user interface on the display (e.g., 450 in FIG. 4) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are, optionally, used for other user interfaces described herein.

Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.

As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector,” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4) while the cursor is over a particular user interface element (e.g., a button, window, slider or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations that include a touch-screen display (e.g., touch-sensitive display system 112 in FIG. 1A) that enables direct interaction with user interface elements on the touch-screen display, a detected contact on the touch-screen acts as a “focus selector,” so that when an input (e.g., a press input by the contact) is detected on the touch-screen display at a location of a particular user interface element (e.g., a button, window, slider or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch-screen display (e.g., by using a tab key or arrow keys to move focus from one button to another button); in these implementations, the focus selector moves in accordance with movement of focus between different regions of the user interface. Without regard to the specific form taken by the focus selector, the focus selector is generally the user interface element (or contact on a touch-screen display) that is controlled by the user so as to communicate the user's intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact). For example, the location of a focus selector (e.g., a cursor, a contact or a selection box) over a respective button while a press input is detected on the touch-sensitive surface (e.g., a touchpad or touch screen) will indicate that the user is intending to activate the respective button (as opposed to other user interface elements shown on a display of the device).

In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90% or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).

For ease of explanation, the description of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold.

User Interfaces And Associated Processes Context-Based Data Detection

Users communicate with each other using electronic devices in many different contexts. In some circumstances, the electronic devices used for communication optionally analyze the communications and detect relevant information in the communications. That relevant information can change depending on the context in which the communications were made. For example, on a first day, a user may communicate with another user while the user is in a first geographic location, and on a second day, the user may communicate with the other user while the user is in a second geographic location. In such circumstances, the relevant information that the electronic devices detect is optionally different depending on whether the user was in the first location or the second location. The embodiments described below provide ways in which electronic devices detect information in communications based on a context of the communications, thereby enhancing the users' interactions with the electronic devices. Enhancing interactions with a device reduces the amount of time needed by a user to perform operations, and thus reduces the power usage of the device and increases battery life for battery-powered devices.

It is understood that people use devices. When a person uses a device, that person is optionally referred to as a user of the device. Thus, in this disclosure, references to a “person” or “people” are optionally interchangeable with references to a “user” or “users”, and references to a “user” or “users” are optionally interchangeable with references to a “person” or “people”.

FIGS. 5A-5O illustrate exemplary ways in which electronic devices select terms in communications between users based on a context of the terms in accordance with some embodiments of the disclosure. The embodiments in these figures are used to illustrate the processes described below, including the processes described with reference to FIGS. 6A-6E.

It should be noted that the examples illustrated in FIGS. 5A-5O are directed to electronic devices having touch screens, though it is understood that the electronic devices need not include touch screens. For example, the electronic devices may include displays without touch-sensitive capability, or the electronic devices may be capable of outputting display information for display on a separate display device, as described previously in this disclosure—in such circumstances, the touch screens described below optionally correspond to the displays mentioned above.

FIG. 5A illustrates exemplary touch screen 112. Touch screen 112 optionally displays one or more user interfaces that include various content. In the example illustrated in FIG. 5A, touch screen 112 optionally displays a messaging application running on an electronic device of which touch screen 112 is a part. The messaging application optionally displays communications between two or more users (e.g., messages 504, 506 and 508). Messages sent from a user of the electronic device of which touch screen 112 is a part (e.g., a first user) to another user (e.g., a second user) are optionally displayed on the right side of touch screen 112 (e.g., messages 504 and 508). Messages received from the other user (e.g., the second user) by the user of the electronic device of which touch screen 112 is a part (e.g., the first user) are optionally displayed on the left side of the touch screen 112 (e.g., message 506). In some embodiments, an identifier of the second user with which the first user is communicating is displayed on touch screen 112 (e.g., “John” in FIG. 5A).

In some embodiments, the electronic device receives terms that correspond to a communication with another user (e.g., voice input or text input including one or more words, phrases, email addresses, etc.). The terms are optionally a message received at the electronic device from another electronic device (e.g., messages 504, 506 and 508). The electronic device optionally determines a current context of the terms (e.g., determines the location of the electronic device, determines terms included in past terms that have been received, etc.), and selects one or more terms in the communications as actionable terms (e.g., terms that can be selected to perform an associated operation) based on word lists that are context-specific. As stated above, in some embodiments, the context is based on the location of the electronic device. For example, in FIG. 5A, the electronic device is optionally located in Los Angeles, as indicated by 502. As a result, the electronic device optionally selects one or more terms in the communications between the first and second users based on a first word list 512 that is optionally associated with Los Angeles. Specifically, the electronic device optionally utilizes the first word list 512, and not the second word list 514, and identifies terms in the communications (e.g., messages 504, 506 and 508) that are included in the first word list 512. In the example illustrated in FIG. 5A, message 506 includes the term “the boat” 510, which is optionally also included in the first word list at 516. As a result, the electronic device optionally selects “the boat” 510 in message 506 as an actionable term. In some embodiments, the actionable term “the boat” is optionally visually distinguished from other terms in the communications (e.g., the actionable terms are one or more of highlighted, underlined, bolded, etc.), as illustrated in FIG. 5A.

In some of the embodiments of the disclosure, an electronic device optionally selects a term as an actionable term when that term is a match for a term in the currently-utilized word list. In some embodiments, a term in a communication matches a term in a word list when the two terms are identical (e.g., case, letters, spacing, etc.). In some embodiments, a term in a communication matches a term in a word list when the two terms are partially identical (e.g., the two terms share some letters, some spacing, some case, etc.). When multiple terms in a currently-utilized word list match the same term in a communication, in some embodiments, the electronic device identifies the word list term that is a better match for the communication term, and selects the communication term as an actionable term based on the better match. In some embodiments, the electronic device selects the communication term as an actionable term based on the multiple matches.

As stated above, in some embodiments, the word list used to select the actionable terms in the communications is based on a current context of the communications. Thus, different actionable terms are optionally selected in different contexts.

FIG. 5B illustrates the electronic device optionally located in New York as opposed to Los Angeles, as in FIG. 5A. The messages 504, 506 and 508 in FIG. 5B optionally include the same terms as the messages in FIG. 5A. However, the electronic device in FIG. 5B is optionally located in New York (as indicated by 502), whereas the electronic device in FIG. 5A was optionally located in Los Angeles (e.g., a current context of the terms in FIG. 5A is optionally different than a current context of the terms in FIG. 5B).

As a result of the different context, the electronic device optionally selects actionable terms using the second word list 514 associated with New York, and not the first word list 512 associated with Los Angeles. Thus, as illustrated in FIG. 5B, the electronic device optionally selects “the game” 520 in message 508 as an actionable term, because “the game” 518 is a term in the second word list 514. Also, the electronic device has optionally not selected “the boat” in message 506 as an actionable term (as it optionally did in FIG. 5A), because “the boat” is a term in the first word list 512, which the electronic device is not utilizing in FIG. 5B.

While the embodiments of the disclosure are described with an electronic device using a single context-dependent word list at a given time, it is understood that more than one context-dependent word list can similarly be used by the electronic devices of the disclosure.

In some embodiments, the current context of the terms of the communication is optionally based on one or more terms in the communication itself, as illustrated in FIG. 5C. In FIG. 5C, touch screen 112 optionally displays messages 522, 524 and 526, similar to before. The electronic device optionally has two word lists to choose from when selecting terms as actionable terms: a first word list 528 associated with vacation destinations, and a second word list 530 associated with movies. It is understood that two words lists are provided by example only, and the scope of the disclosure extends to any number of available word lists.

Message 524 optionally includes the term “vacation” 536. As a result, the electronic device optionally uses the first word list 528, which is optionally associated with vacations, to select actionable terms in messages 522, 524 and 526. Specifically, the electronic device optionally selects “Italy” 538 and “Spain” 540 in message 524 as actionable terms, because “Italy” 532 and “Spain” 534 are optionally included in the first word list 528.

FIG. 5D illustrates an electronic device that has the same word lists available to it as the electronic device in FIG. 5C, except that the messages in FIG. 5D differ from those in FIG. 5C. In FIG. 5D, the communications optionally include the term “movie” 544 in message 542 instead of the term “vacation,” as in FIG. 5C. As a result, the electronic device optionally uses the second word list 530, which is optionally associated with movies, to select actionable terms in messages 522, 542 and 526. Specifically, the electronic device optionally selects “cruise” 546 in message 526 as an actionable term, because “Tom Cruise” 548 is optionally included in the second word list 530.

In some embodiments, the electronic device optionally obtains content associated with the actionable terms it identifies. FIG. 5E illustrates the electronic device obtaining content associated with an actionable term. Specifically, the term “the Game” 520 in message 508 has optionally been selected by the electronic device as an actionable term as previously described in FIGS. 5A-5D, for example. The electronic device optionally further obtains content 550 associated with “the game” 520. Because the electronic device optionally recognizes “the game” 520 as referring to a game between the Knicks and the Lakers (e.g., because the “the game” in the word list used by the electronic device is optionally associated with content), the electronic device is optionally able to obtain content relating to that game.

In the embodiment illustrated in FIG. 5E, the content 550 optionally includes information about the teams that are involved in “the game” (e.g., Knicks and Lakers), the time of the game (e.g., 7:30 pm ET), the location of the game, a TV station on which the game will be broadcasted, the record of the Knicks, and the record of the Lakers. In some embodiments, the electronic device optionally obtains alternative or additional content to the content illustrated in FIG. 5E. In some embodiments, the obtained content is a link to additional content associated with one or more of the actionable terms (e.g., “the game”). In some embodiments, the link is a link to an application on the electronic device (e.g., the determined content is in an application on the electronic device, such as an application that has information about restaurants, and the link is a link to information about a particular restaurant in the application).

In some embodiments, the electronic device only obtains content associated with an actionable term after detecting selection of the actionable term. FIG. 5F illustrates selection of an actionable term (e.g., “the game” 520) in accordance with some embodiments. As in FIG. 5E, the term “the Game” 520 in message 508 has optionally been selected by the electronic device as an actionable term as previously described in FIGS. 5A-5D, for example. A user has optionally selected “the Game” 520 by touching touch screen 112 using finger 552, as illustrated in FIG. 5F. Touch input using touch screen 112 is provided by way of example only, and it is understood that other ways of selecting actionable terms are also within the scope of the disclosure (e.g., mouse input, keyboard input, voice input, etc.).

In response to the selection of “the Game” 520 in FIG. 5F, the electronic device optionally obtains content 550 associated with “the Game” 520, as illustrated in FIG. 5G. Content 550 can be as described with reference to FIG. 5E.

In some embodiments, the electronic device displays the obtained content along with the communications between the users, and in some embodiments, communicates the obtained content to the other user. FIG. 5H illustrates obtained content 550 from FIGS. 5E and/or 5G displayed as content 554 along with messages 506 and 508 on touch screen 112. In some embodiments, content 554 is also communicated from one user to the other user by the electronic device (e.g., from the first user to the second user, or from the second user to the first user, in the messaging application). Content 554 optionally corresponds to content 550 in FIGS. 5E and/or 5G.

In some embodiments, the actionable terms are selectable, and in some embodiments, the electronic device performs an operation in response to selection of an actionable term based on a type of the actionable term (e.g., making a phone call to an actionable term that is a detected phone number, sending an email to an actionable term that is a detected email address, performing a search on an actionable term that is a detected search term, displaying content associated with the actionable term, etc.). For example, Fig. SI illustrates messages 504, 506 and 508 with the term “the Game” 520 having been selected as an actionable term as previously described in FIGS. 5A-5D, for example. The term “the Game” 520 is optionally selectable, and selection of the term “the Game” optionally causes the electronic device to perform an operation based on the type of the term “the Game,” as will be described below. A user has selected “the Game” 520 with finger 552 in FIG. 5I.

In response to the selection of “the Game” 520 in FIG. 5I, the electronic device optionally allows for the purchase of tickets for the Knicks vs. Lakers game corresponding to the term “the Game” 520 in FIG. 5J. Specifically, the electronic device optionally displays a ticket purchase user interface element 556 along with messages 506 and 508 on touch screen 112. A user can then choose options for the tickets to be purchased (e.g., quantity, section, seat number, price, etc.), and can purchase the tickets from the electronic device (e.g., by selecting the “Buy Now” button).

In some embodiments, in addition to selecting terms as actionable terms based on context-specific word lists, the electronic device optionally selects terms as actionable terms based on a standard word list (e.g. a word list that is not based on the current context of the terms of the communications, such as email addresses, websites, street addresses, etc.). In some embodiments, the actionable terms selected based on the standard word list optionally operate in the same way and are visually distinguished in the same way as the actionable terms selected based on the first or second context-dependent word lists. FIG. 5K illustrates an electronic device with access to three word lists: one standard word list 558, a first word list 528 associated with vacation destinations, and a second word list 530 associated with movies. Similar to the examples described above with reference to FIG. 5D, the electronic device optionally selects the term “cruise” 546 in message 564 as a result of the term “movie” 544 in message 542 (e.g., the current context) causing the electronic device to utilize the second word list 530 to select actionable terms—the term “Tom Cruise” 548 is optionally included in the second word list 530.

However, additionally, the electronic device optionally has a standard word list 558 based upon which the electronic device additionally selects actionable terms regardless of the current context of the communications. Thus, the electronic device has additionally selected the term “iPhone” 560 in message 564 as an actionable term, because the term “iPhone” 562 is optionally included in the standard word list 558.

In some embodiments, in addition to selecting terms as actionable terms based on context-specific word lists, the electronic device optionally selects terms as actionable terms based on regular expressions. For example, the detected occurrence of special symbols such as the @ symbol are used to identify email addresses, xxx-xxx-xxxx formats are used to identify phone numbers, “www.” prefixes are used to identify uniform resource locators that correspond to webpages, etc. In some embodiments, the actionable terms selected based on the regular expressions optionally operate in the same way (e.g., provide additional content upon selection) and are visually distinguished in the same way as the actionable terms selected based on the first or second context-dependent word lists. FIG. 5L illustrates an electronic device that optionally selects actionable terms based on context-specific word lists and regular expressions. Touch screen 112 optionally displays messages 522, 544 and 565. Further, the electronic device has optionally selected the term “cruise” 546 as an actionable term, as described with reference to FIG. 5K.

However, additionally, the electronic device has optionally selected the term “123-456-7890” 566 in message 565 as an actionable term, because the term “123-456-7890” 566 optionally has the format of a telephone number. As a result, the electronic device optionally selects the term “123-456-7890” 566 as an actionable term, and the user can optionally select the term to perform an appropriate operation (e.g., to call the phone number 123-456-7890 from the electronic device or other device).

In some embodiments, the electronic device searches for certain keywords in the communications, each of which is optionally associated with a word list with which to select actionable terms in the communications. In response to detecting the existence of one of the keywords in the communications, the electronic device optionally uses the word list associated with the keyword to select actionable terms. In some embodiments, the electronic device uses the word lists associated with the keywords only for a predetermined time period (e.g., 5, 15 or 30 minutes) after detecting the existence of the keywords in the communications. FIG. 5M illustrates an electronic device that searches for keywords 574 in communications with a user, and has access to various word lists that are associated with the keywords. Specifically, the electronic device optionally has keywords 574. The “politics” keyword is optionally associated with the politics word list 576. The “San Francisco” keyword is optionally associated with the San Francisco word list 578. The “Lakers” keyword is optionally associated with the Lakers word list 580. Touch screen 112 optionally displays messages 568, 570 and 572 corresponding to communications between a first user and a second user.

In FIG. 5N, the electronic device has optionally identified the term “Lakers” 584 in message 570 as matching the term “Lakers” 582 in keywords 574. As a result, in FIG. 5O, the electronic device optionally uses the Lakers word list 580 to select actionable terms in messages 568, 570 and 572. Specifically, the electronic device has optionally selected the terms “Kobe” 586 and “Phil Jackson” 588 in message 570 as actionable terms, because the terms “Kobe Bryant” 590 and “Phil Jackson” 592 are optionally included in the Lakers word list 580. The electronic device optionally utilizes multiple word lists in response to detection of multiple keywords in messages 568, 570 and 572.

FIGS. 6A-6E are flow diagrams illustrating a method 600 of selecting terms in communications between users based on a context of the terms in accordance with some embodiments. The method 600 is optionally performed at an electronic device such as device 100 or device 300 as described above with reference to FIGS. 1A-1B and 2-3. Some operations in method 600 are, optionally, combined and/or the order of some operations is, optionally, changed.

As described below, the method 600 provides ways in which a device optionally selects terms as actionable terms in communications. The method reduces the cognitive burden on a user when interacting with a user interface of the device of the disclosure, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, increasing the efficiency of the user's interaction with the user interface conserves power and increases the time between battery charges.

In some embodiments, an electronic device (e.g., device 100 or 300) with one or more processors and memory receives (602) a plurality of terms that correspond to a communication with another user (e.g., voice input or text input including one or more words, phrases, email addresses, etc.). The terms are optionally a message received at the electronic device from another electronic device, such as messages 504, 506 and 508 in FIG. 5A.

The electronic device optionally determines (604) a current context of the plurality of terms (e.g., determines the location of the electronic device, determines terms included in past terms that have been received, etc.). In some embodiments, the current context of the plurality of terms is based on one or more of: a current application on the electronic device, a time of day, one or more recently used applications on the electronic device, a location of the electronic device, and previously received terms on the electronic device (606) (e.g., certain previously received terms optionally trigger certain word lists). For example, “movie” triggers movie title wordlist, “dinner” triggers restaurant word list, “game” triggers sports word list, “TV” triggers television show word list, etc. FIGS. 5A-5D illustrate some of these contexts.

In some embodiments, in accordance with a determination that the current context is a first context (e.g., determining that the electronic device is in a first location, such as in FIG. 5A), the electronic device selects (608) one or more terms in the plurality of terms based on a first word list (e.g., word list 512 in FIG. 5A) as actionable terms (e.g., selecting terms in the plurality of terms that match words in the first word list). In some embodiments, the first context is based on one or more of activities of a user of the electronic device, a time of day, a currently-utilized application on the electronic device, current news events, calendar information on the electronic device (e.g., appointment information), location interests of a user of the electronic device, and content on the electronic device (610) (e.g., music, video, books on the electronic device). In some embodiments, selecting the one or more terms in the plurality of terms comprises (612) determining (614) a context associated with a first term in the plurality of terms, and selecting (616) the one or more terms based on the context associated with the first term (e.g., as illustrated in FIGS. 5C-5D).

In some embodiments, in accordance with a determination that the current context is a second context, different from the first context (e.g., determining that the electronic device is in a second location, different from the first location, such as in FIG. 5B), the electronic device selects (618) one or more terms in the plurality of terms as actionable terms based on a second word list (e.g., word list 514 in FIG. 5B), different from the first word list (e.g., identifying terms in the plurality of terms that match words in the second word list). In some embodiments, the second context is based on one or more of activities of a user of the electronic device, a time of day, a currently-utilized application on the electronic device, current news events, calendar information on the electronic device, location interests of a user of the electronic device, and content on the electronic device (620). In some embodiments, the first and second word lists are provided by one or more applications on the electronic device (622) (e.g., third party applications can provide their own word lists which are also, optionally, updated over time). In some embodiments, a first application on the electronic device and a second application on the electronic device provide different word lists (624).

In some embodiments, the plurality of terms that corresponds to the communication with the other user is received from a second electronic device (e.g., the other user sends a text message from the other user's electronic device), and the first and second word lists are based on information from the second electronic device (626) (e.g., if a second user's device triggered data detection for a word or phrase, then that word or phrase is optionally flagged for data detection by the current user's device). In some embodiments, selecting the one or more terms in the plurality of terms comprises (628) determining (630) a context associated with a first term in the plurality of terms, and selecting (632) the one or more terms based on the context associated with the first term (e.g., look for key terms (e.g., movie names, TV show names, reservation information, restaurant names, etc.), and then do data detection around the key terms using a word list that is specific to those key terms, as illustrated in FIGS. 5M-5O). For example, the electronic device optionally identifies the name of a sports team in the plurality of terms, and then uses a word list associated with that sports team to identify other terms around the name of the sports team.

In some embodiments, the electronic device displays (634) the plurality of terms (e.g., in a messaging application), wherein one or more of the actionable terms are visually distinguished from other terms (e.g., the actionable terms are one or more of highlighted, underlined, bolded, etc.), such as illustrated in FIGS. 5A-5L and 5O.

In some embodiments, the electronic device obtains (636) content associated with one or more of the actionable terms (e.g., the device identifies and retrieves content from a content source, the content associated with the actionable terms, such as content 550 in FIG. 5E). For example, if one of the actionable terms is the name of a movie, the retrieved content is optionally information about the movie, such as actors, show times, box office statistics, etc. Obtaining the content optionally comprises obtaining a link to additional content associated with one or more of the actionable terms (638). The link optionally comprises a link to an application on the electronic device (640) (e.g., the determined content is in an application on the electronic device, such as an application that has information about restaurants, and the link is a link to information about a particular restaurant in the application).

In some embodiments, the electronic device communicates (642) the plurality of terms and the obtained content to the other user (e.g., communicate the plurality of terms to the other user, such as in a text message, with the content in-line with the plurality of terms), as illustrated in FIG. 5H.

In some embodiments, the plurality of terms is to be communicated to the other user from the electronic device (e.g., the plurality of terms is part of an outgoing text message), and the first word list and the second word list correspond to a user of the electronic device (644) (e.g., the first and second word lists are based on information about a user of the electronic device). In some embodiments, the plurality of terms is received from the other user of a second electronic device (e.g., the plurality of terms is part of an incoming text message), and the first word list and the second word list correspond to the other user of the second electronic device (646) (e.g., the first and second word lists are based on information about the other user of the second electronic device). In some embodiments, the first word list and the second word list correspond to a user of the electronic device and the other user of a second electronic device (648) (e.g., the first and second word lists are based on information about a user of the electronic device and information about the other user of the second electronic device).

In some embodiments, prior to obtaining the content associated with the one or more of the actionable terms, the electronic device receives (650) a selection of the one or more of the actionable terms (e.g., detecting a touch input on the one or more of the actionable terms), as illustrated in FIG. 5F. In response to receiving the selection of the one or more of the actionable terms, the electronic device optionally obtains (652) the content associated with the selected actionable terms, as illustrated in FIG. 5G.

In some embodiments, selection of an actionable term causes performance of an operation associated with the selected actionable term (654) (e.g., making a phone call to an actionable term that is a detected phone number, sending an email to an actionable term that is a detected email address, performing a search on an actionable term that is a detected search term, displaying content associated with the actionable term, etc.). In some embodiments, the electronic device detects (656) a selection of one of the actionable terms, and in response to the selection, performs (658) an operation associated with the selected actionable term, wherein the operation is dependent on a type of the selected actionable term (e.g., search locations for an address when the selected actionable term is an address, search TV listings for a TV show when the selected actionable term is a TV show, search restaurant ratings for a restaurant when the selected actionable term is the name of a restaurant, search sports scores for a sports team when the selected actionable term is the name of a sports team), as illustrated in FIGS. 5J-5K.

In some embodiments, the electronic device selects (660) one or more terms in the plurality of terms as actionable terms based on a standard word list (e.g. a word list that is not based on the current context of the plurality of terms, such as email addresses, websites, street addresses, etc., such as word list 558 in FIG. 5K). In some embodiments, the actionable terms selected based on the standard word list optionally operate in the same way and are visually distinguished in the same way as the actionable terms selected based on the first or second context-dependent word lists, as illustrated in FIG. 5K. In some embodiments, the electronic device selects (662) one or more terms in the plurality of terms as actionable terms based on regular expressions, as illustrated in FIG. 5L. For example, the detected occurrence of special symbols such as the @ symbol are used to identify email addresses, (xxx) xxx-xxxx format is used to identify phone numbers, “www.” prefix is used to identify uniform resource locators that correspond to webpages, etc. In some embodiments, the actionable terms selected based on the regular expressions optionally operate in the same way (e.g., provide additional content upon selection) and are visually distinguished in the same way as the actionable terms selected based on the first or second context-dependent word lists, as illustrated in FIG. 5L. In some embodiments, the electronic device receives (664) updates to the first and second word lists at intervals of time (e.g., regular intervals of time, such as once a week or based on current events or changing seasons). In some embodiments, updates to the first and second wordlists add words. In some embodiments, updates to the first and second wordlists remove words. In some embodiments, updates to the first and second wordlists add words and remove words (e.g., so as to provide a more relevant list of words without dramatically increasing the overall number of words that are being detected).

In some embodiments, the electronic device receives (666) a first plurality of terms at a first time (e.g., receiving a first text message). The plurality of terms that corresponds to the communication with the other user optionally comprises a second plurality of terms received at a second time, later than the first time (668) (e.g., receiving a second text message after the first text message). Selecting the one or more terms in the second plurality of terms as the actionable terms optionally comprises, in accordance with a determination that the second plurality of terms was received after the first plurality of terms, selecting (670) the one or more terms in the second plurality of terms as the actionable terms (e.g., selecting terms as actionable terms in the more recently-received text message). In some embodiments, in accordance with the determination that the second plurality of terms was received after the first plurality of terms, the electronic device forgoes selecting (672) one or more terms in the first plurality of terms as actionable terms (e.g., do not select terms as actionable terms in the earlier-received text message).

In some embodiments, in accordance with a determination that the plurality of terms includes a first term, the electronic device utilizes (674) a third word list and a fourth word list associated with the first term for selecting one or more terms in the plurality of terms as actionable terms for a predetermined time period (e.g., 5, 15 or 30 minutes), wherein the third and fourth words lists are different from the first and the second word lists (e.g., certain terms in the plurality of terms cause the word lists used to identify terms to change for a predetermined time period). For example, if the plurality of terms includes the name of a movie, the electronic device changes the word lists to be used for the next five minutes, for example, to word lists associated with the movie.

It should be understood that the particular order in which the operations in FIGS. 6A-6E have been described is merely exemplary and is not intended to indicate that the described order is the only order in which the operations could be performed. One of ordinary skill in the art would recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., method 800) are also applicable in an analogous manner to method 600 described above with respect to FIGS. 6A-6E. For example, the plurality of terms, first word list, second word list and actionable terms described above with reference to method 600 optionally have one or more of the characteristics of the plurality of terms, first word list and actionable terms described herein with reference to other methods described herein (e.g., method 800). For brevity, these details are not repeated here.

The operations in the information processing methods described above are, optionally, implemented by running one or more functional modules in an information processing apparatus such as general purpose processors (e.g., as described above with respect to FIGS. 1A and 3) or application specific chips.

The operations described above with reference to FIGS. 6A-6E are, optionally, implemented by components depicted in FIGS. 1A-1B and 9. For example, receiving operation 602, determining operation 604, and selecting operations 608 and 618 are, optionally, implemented by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112, and event dispatcher module 174 delivers the event information to application 136-1. A respective event recognizer 180 of application 136-1 compares the event information to respective event definitions 186, and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub-event, such as selection of an object on a user interface. When a respective predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally utilizes or calls data updater 176 or object updater 177 to update the application internal state 192. In some embodiments, event handler 190 accesses a respective GUI updater 178 to update what is displayed by the application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in FIGS. 1A-1B and 9.

Automatic Content Population

Automatically populating a user interface with content associated with a user's actions (e.g., communications) on an electronic device can enhance the user's interaction with the content and the device. Such automatic population in the context of communications between users can similarly enhance each user's interaction with the content and their respective devices. The embodiments described below provide ways that a device optionally automatically populates a user interface with content. Enhancing interactions with a device reduces the amount of time needed by a user to perform operations, and thus reduces the power usage of the device and increases battery life for battery-powered devices.

FIGS. 7A-7F illustrate exemplary ways in which an electronic device automatically populates a user interface with content in accordance with some embodiments of the disclosure. The embodiments in these figures are used to illustrate the processes described below, including the processes described with reference to FIGS. 8A-8C.

It should be noted that the examples illustrated in FIGS. 7A-7F are directed to electronic devices having touch screens, though it is understood that the electronic devices need not include touch screens. For example, the electronic devices may include displays without touch-sensitive capability, or the electronic devices may be capable of outputting display information for display on a separate display device, as described previously in this disclosure—in such circumstances, the touch screens described below optionally correspond to the displays mentioned above.

FIG. 7A illustrates exemplary touch screen 112. Touch screen 112 optionally displays one or more user interfaces that include various content. In the example illustrated in FIG. 7A, touch screen 112 optionally displays a messaging application running on an electronic device of which touch screen 112 is a part, as described with reference to FIGS. 5A-50. The messaging application optionally displays communications between two or more users (e.g., messages 702 and 704). Messages sent from a user of the electronic device of which touch screen 112 is a part (e.g., a first user) to another user (e.g., a second user) are optionally displayed on the right side of touch screen 112 (e.g., message 704). Messages received from the other user (e.g., the second user) by the user of the electronic device of which touch screen 112 is a part (e.g., the first user) are optionally displayed on the left side of the touch screen 112 (e.g., message 702). In some embodiments, an identifier of the second user with which the first user is communicating is displayed on touch screen 112 (e.g., “John” in FIG. 7A).

In some embodiments, the electronic device receives terms that correspond to a communication with another user (e.g., voice input or text input including one or more words, phrases, email addresses, etc.). The terms are optionally a message received at the electronic device from another electronic device. In some embodiments, the electronic device optionally identifies one or more terms in messages 702 and 704 as actionable terms (e.g., terms that can be selected to perform an associated operation), similar to the examples discussed with reference to FIGS. 5A-5O. In some embodiments, the actionable terms are identified using a word list, such as movies word list 706, which, in the example illustrated in FIG. 7A, optionally includes the names of various movies. It is understood, however, that the electronic device can identify terms as actionable terms in other ways within the scope of the disclosure.

FIG. 7B illustrates identification of an actionable term in messages 702 and 704. Specifically, the electronic device has identified the term “the Skateboard” 708 in message 704. The electronic device has done so in the example illustrated in FIG. 7B because the term “The Skateboard” 712 is included in movies word list 706, similar to the examples described previously with reference to FIGS. 5A-5D.

Additionally, the electronic device has optionally obtained related content 710 associated with the term “the Skateboard” 708, and concurrently displayed a representation of the content 710 along with messages 702 and 704 (e.g., the electronic device has optionally displayed the content in-line with or otherwise in close proximity to the received plurality of terms (e.g., messages 704 and 702) displayed in the user interface). The electronic device optionally obtains content 710 in a manner similar to the examples described with reference to FIGS. 5E-5H. For example, if an identified term is the name of a movie, the electronic device optionally obtains information about the movie and displays the information in the user interface adjacent to or otherwise in close proximity to the identified actionable term—the information optionally is information such as actors, show times, box office statistics, etc. In the example illustrated in FIG. 7B, the related content 710 includes the name of the movie (e.g., The Skateboard: The Movie), a summary of the movie, and a list of actors and actresses starring in the movie, though it is understood that other related content can additionally or alternatively be obtained and displayed by the electronic device.

In some embodiments, the electronic device identifies actionable terms based on regular expressions, similar to the example described with reference to FIG. 5L. For example, the detected occurrence of special symbols such as the @ symbol are optionally used to identify email addresses, (xxx) xxx-xxxx formats are optionally used to identify phone numbers, “www.” prefixes are optionally used to identify uniform resource locators that correspond to webpages, etc. FIG. 7C illustrates messages 702 and 714 displayed on touch screen 112. In FIG. 7D, the electronic device has optionally identified an actionable term in messages 702 and 714 based on a regular expression. Specifically, the electronic device has optionally identified the term “www.skateboardmovie.com” 716 in message 714 based on, for example, a prefix of “www.” Additionally, the electronic device has optionally obtained content 718 associated with the term “www.skateboardmovie.com” 716 (e.g., a preview of the website), and has concurrently displayed the content 718 along with messages 702 and 714 in the user interface. In the example illustrated in FIG. 7D, the related content 718 includes a short description of the movie from the website, as well as a link to a preview of the movie, though it is understood that other content is similarly within the scope of the disclosure. In some embodiments, as in FIG. 7D, the related content is actionable (e.g., the related content allows a user to perform some action related to the content and/or its associated term—for example, making a dinner reservation, purchasing tickets for a movie, etc., such as described with reference to FIG. 5J).

In some embodiments, the obtained related content includes transaction options for an event (e.g., for the movie). FIG. 7E illustrates messages 702 and 704 (as illustrated in FIGS. 7A-7B) and related content 720 for The Skateboard movie that includes the ability to buy tickets for the movie. Specifically, the related content 720 allows for selection of a show time for the movie, and indication of a number of tickets to purchase. It is understood that other embodiments may include additional or alternative content to the content in FIG. 7E.

In some embodiments, the electronic device is more proactive in identifying actionable terms and/or displaying related content for actionable terms for more recently-received terms than for less recently-received terms, thus conserving processing resources while still providing robust data detection for recent communications that a user is most likely to be reviewing. FIG. 7F illustrates two messages received at separate times. Specifically, message 722 was optionally received by the electronic device from another user at a first time. Message 724 was optionally received by the electronic device from the user of the electronic device (e.g., the user optionally typed-in message 724 to respond to message 722) at a second time, later than the first time.

In the example illustrated in FIG. 7F, the electronic device optionally has two word lists with which to identify actionable terms in messages 722 and 724. The first word list 728 is optionally a word list for use in identifying actionable terms in older messages (e.g., message 722), and the second word list 730 is optionally a word list for use in identifying actionable terms in recent messages (e.g., message 724). The second word list 730 optionally includes all of the terms in the first word list 728, in addition to extra terms of its own (e.g., the term “The Skateboard” 736), though it is understood that this need not be the case.

The electronic device has identified the term “I Love Pizza” 738 in message 722 as an actionable term using the first word list 728. The electronic device has also optionally identified the terms “The Skateboard” 742 and “I Love Pizza” 740 in message 724 as actionable terms using the second word list 730. Thus, the electronic device has identified actionable terms in an older message using one word list, and has identified actionable terms in a more recent message using a different word list. In some embodiments, the electronic device identifies a term as actionable only in the more recent message, even if the term also exists in the older message.

Additionally, the electronic device has not displayed content associated with the term “I Love Pizza” 738 in message 722, but has displayed content 726 associated with the term “I Love Pizza” 740 in message 724. Thus, the electronic device has displayed content for actionable terms identified in more recent messages, but has not displayed content for actionable terms identified in older messages so as to provide additional content for messages that a user is likely to look at, but not for messages that the user is less likely to look at, thereby improving the user experience without unnecessarily using processing resources. In the example illustrated in FIG. 7F, the related content 726 optionally includes the name of the restaurant, a description of the restaurant, and the ability to make reservations at the restaurant by supplying a reservation time and a party size, though it is understood that the related content 726 can include additional or alternative content to that illustrated in FIG. 7F.

FIGS. 8A-8C are flow diagrams illustrating a method 800 of automatically populating a user interface with content in accordance with some embodiments. The method 800 is optionally performed at an electronic device such as device 100 or device 300 as described above with reference to FIGS. 1A-1B and 2-3. Some operations in method 800 are, optionally, combined and/or the order of some operations is, optionally, changed.

As described below, the method 800 provides ways in which a device optionally automatically populates a user interface with content. The method reduces the cognitive burden on a user when interacting with a user interface on the device, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, increasing the efficiency of the user's interaction with the user interface conserves power and increases the time between battery charges.

In some embodiments, an electronic device with one or more processors and memory generates (802) a user interface for display on a display device (e.g., as illustrated in FIG. 7A). While the user interface is displayed on the display device, the electronic device optionally receives (804) a plurality of terms that corresponds to a communication with another user (e.g., voice input or text input including one or more words, phrases, email addresses, etc., such as messages 702 and 704 in FIG. 7A). The terms are optionally received at the electronic device from another electronic device. In some embodiments, the plurality of terms includes a first set of terms received at a first time (e.g., receiving a first text message, such as message 702 in FIG. 7A) and a second set of terms received at a second time (e.g., message 704 in FIG. 7A) that was after the first time (806). In some embodiments, the received plurality of terms includes a name of a movie (808), as illustrated in FIG. 7B.

In some embodiments, after receiving the plurality of terms, the electronic device identifies (810) one or more terms in the plurality of terms as actionable terms (e.g., terms that can be selected to perform an associated operation), as illustrated in FIG. 7B. Identifying the one or more terms in the plurality of terms as the actionable terms is optionally based on regular expressions (812), as illustrated in FIG. 7D. For example, the detected occurrence of special symbols such as the @ symbol are used to identify email addresses, (xxx) xxx-xxxx formats are used to identify phone numbers, “www.” prefixes are used to identify uniform resource locators that correspond to webpages, etc. In some embodiments, identifying the one or more terms in the plurality of terms as the actionable terms is based on a first word list (814), as illustrated in FIGS. 7A-7B (e.g., the electronic device identifies terms in the plurality of terms that match words in the first word list). In some embodiments, the plurality of terms is optionally received from a second electronic device (e.g., the other user sends a text message from the other user's electronic device), and the first word list is optionally based on information from the second electronic device (816) (e.g., if a second user's device triggered data detection for a word or phrase, then that word or phrase is optionally flagged for data detection by the current user's device).

In some embodiments, identifying one or more terms in the plurality of terms as actionable terms includes comparing the first set of terms to a first word list and comparing the second set of terms to a second word list that includes more terms than the first word list (818), as illustrated in FIG. 7F. In some embodiments, the first set of terms is a subset of the second set of terms. Thus, in some embodiments, more aggressive data detection is used for more recent text (e.g., more recently received messages), so as to conserve processing resources while still providing robust data detection for recent communications that the user is most likely to be reviewing. In some embodiments, identifying one or more terms in the plurality of terms as actionable terms includes identifying one or more actionable terms in the first set of terms, and identifying one or more actionable terms in the second set of terms (820), as illustrated in FIG. 7F. In some embodiments, identifying the one or more terms in the plurality of terms comprises (822) determining (824) a context associated with a first term in the plurality of terms, and identifying (826) the one or more terms based on the context associated with the first term (e.g., the electronic device optionally look for key terms (e.g., movie names, TV show names, reservation information, restaurant names, etc.), and then does data detection around the key terms using a word list that is specific to those key terms, similar to the examples described with reference to FIGS. 5M-5O). For example, the electronic device optionally identifies the name of a sports team in the plurality of terms, and then uses a word list associated with that sports team to identify other terms around the name of the sports team. In some embodiments, one of the actionable terms comprises the name of the movie (828), as illustrated in FIGS. 7B and 7E-7F.

In some embodiments, the electronic device obtains (830) related content associated with the identified one or more terms, as illustrated in FIGS. 7B and 7D-7F (e.g., the device identifies and retrieves content from a content source, the content associated with the identified one or more terms). For example, if one of the identified terms is the name of a movie, the retrieved content is optionally information about the movie, such as actors, show times, box office statistics, etc. In some embodiments, the related content is actionable (832) (e.g., the related content allows a user to perform some action related to the content and/or its associated term, such as making a dinner reservation, purchasing tickets for a movie, etc.). In some embodiments, the related content includes information about an event (834), as illustrated in FIG. 7B (e.g., menu for a dinner, show times for a movie, venue information for a game, hours of operation of a restaurant, menu for the restaurant, sports scores for a sporting event, game start time for a sporting event, etc.). In some embodiments, the related content includes transaction options for an event (836), as illustrated in FIG. 7E (e.g., purchasing tickets (sports or non-sports) for an event, reserving tables for a dinner, etc.). In some embodiments, the related content comprises show times for the movie at one or more theaters that are local to the electronic device (838), as illustrated in FIG. 7E. In some embodiments, the related content comprises a link to purchase one or more tickets for the movie at one or more theaters that are local to the electronic device (840), as illustrated in FIG. 7E.

In some embodiments, after obtaining the related content, the electronic device concurrently displays (842) a representation of the related content along with the received plurality of terms, as illustrated in FIGS. 7B and 7D-7F (e.g., the electronic device displays the content in-line with or otherwise in close proximity to the received plurality of terms displayed in the user interface). For example, if an identified term is the name of a movie, the electronic device optionally displays information about the movie, such as actors, show times, box office statistics, etc., adjacent to the identified term. In some embodiments, concurrently displaying a representation of the related content along with the received plurality of terms includes displaying the related content for one or more of the actionable terms in the second set of terms without displaying related content for any of the actionable terms in the first set of terms (844), as illustrated in FIG. 7F. In some embodiments, even if the same actionable term is identified in an earlier message and a later message, the related content is displayed for the later message but not for the earlier message, so as to provide additional content for messages that the user is likely to look at but not for messages that the user is less likely to look at, thereby improving the user experience without unnecessarily using processing resources. In some embodiments, the identified actionable terms are visually distinguished from other terms (846) (e.g., the actionable terms are one or more of highlighted, underlined, bolded, etc.).

In some embodiments, in accordance with a determination that the plurality of terms includes a first term, the electronic device utilizes (848) a second word list for identifying one or more terms in the plurality of terms as actionable terms for a predetermined time period (e.g., 5, 15 or 30 minutes), wherein the first word list is different from the second word list (e.g., certain terms in the plurality of terms optionally cause the word list used to identify terms to change for a predetermined time period). For example, if the plurality of terms includes the name of a movie, the word list to be used for the next 5 minutes is optionally changed, for example, to a word list associated with the movie.

It should be understood that the particular order in which the operations in FIGS. 8A-8C have been described is merely exemplary and is not intended to indicate that the described order is the only order in which the operations could be performed. One of ordinary skill in the art would recognize various ways to reorder the operations described herein. Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., method 600) are also applicable in an analogous manner to method 800 described above with respect to FIGS. 8A-8C. For example, the plurality of terms, first word list and actionable terms described above with reference to method 800 optionally have one or more of the characteristics of the plurality of terms, first word list, second word list and actionable terms described herein with reference to other methods described herein (e.g., method 600). For brevity, these details are not repeated here.

The operations in the information processing methods described above are, optionally, implemented by running one or more functional modules in an information processing apparatus such as general purpose processors (e.g., as described above with respect to FIGS. 1A and 3) or application specific chips.

The operations described above with reference to FIGS. 8A-8C are, optionally, implemented by components depicted in FIGS. 1A-1B and 10. For example, generating operation 802, receiving operation 804, and identifying operation 810 are, optionally, implemented by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112, and event dispatcher module 174 delivers the event information to application 136-1. A respective event recognizer 180 of application 136-1 compares the event information to respective event definitions 186, and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub-event, such as selection of an object on a user interface. When a respective predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally utilizes or calls data updater 176 or object updater 177 to update the application internal state 192. In some embodiments, event handler 190 accesses a respective GUI updater 178 to update what is displayed by the application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in FIGS. 1A-1B and 10.

In accordance with some embodiments, FIG. 9 shows a functional block diagram of an electronic device 900 configured in accordance with the principles of the various described embodiments. The functional blocks of the device are, optionally, implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described embodiments. It is understood by persons of skill in the art that the functional blocks described in FIG. 9 are, optionally, combined or separated into sub-blocks to implement the principles of the various described embodiments. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

As shown in FIG. 9, an electronic device 900 optionally includes a receiving unit 902 configured to receive inputs, a processing unit 904 coupled to the receiving unit 902, a communicating unit 916 coupled to the receiving unit 902 and the processing unit 904 and configured to communicate data, and a detecting unit 918 coupled to the communicating unit 916 and the processing unit 904 and configured to detect inputs. In some embodiments, the processing unit 904 includes a display enabling unit 906, a determining unit 908, a selecting unit 910, an obtaining unit 912 and a performing unit 914.

In some embodiments, the receiving unit 902 is configured to receive a plurality of terms that corresponds to a communication with another user. In some embodiments, the processing unit 904 is configured to determine a current context of the plurality of terms (e.g., with the determining unit 908). In some embodiments, the processing unit 904 is configured to, in accordance with a determination that the current context is a first context, select (e.g., with the selecting unit 910) one or more terms in the plurality of terms based on a first word list as actionable terms. In some embodiments, the processing unit 904 is configured to, in accordance with a determination that the current context is a second context, different from the first context, select (e.g., with the selecting unit) one or more terms in the plurality of terms as actionable terms based on a second word list, different from the first word list. In some embodiments, the processing unit 904 is configured to display (e.g., with the display enabling unit 906) the plurality of terms, wherein one or more of the actionable terms are visually distinguished from other terms.

In some embodiments, the processing unit 904 is configured to obtain (e.g., with the obtaining unit 912) content associated with one or more of the actionable terms. In some embodiments, the communicating unit 916 is configured to communicate the plurality of terms and the obtained content to the other user. In some embodiments, obtaining the content comprises obtaining (e.g., with the obtaining unit 912) a link to additional content associated with one or more of the actionable terms. In some embodiments, the link comprises a link to an application on the electronic device.

In some embodiments, the receiving unit 902 is configured to, prior to obtaining the content associated with the one or more of the actionable terms, receive a selection of the one or more of the actionable terms. In some embodiments, the processing unit 904 is configured to, in response to receiving the selection of the one or more of the actionable terms, obtain (e.g., with the obtaining unit 912) the content associated with the selected actionable terms.

In some embodiments, selection of an actionable term causes performance of an operation (e.g., with the performing unit 914) associated with the selected actionable term. In some embodiments, the detecting unit 918 is configured to detect a selection of one of the actionable terms. In some embodiments, the processing unit 904 is configured to, in response to the selection, perform an operation (e.g., with the performing unit 914) associated with the selected actionable term, wherein the operation is dependent on a type of the selected actionable term.

In some embodiments, the processing unit 904 is configured to select (e.g., with the selecting unit 910) one or more terms in the plurality of terms as actionable terms based on a standard word list. In some embodiments, the processing unit 904 is configured to select (e.g., with the selecting unit 910) one or more terms in the plurality of terms as actionable terms based on regular expressions.

In some embodiments, the first and second contexts are based on one or more of activities of a user of the electronic device, a time of day, a currently-utilized application on the electronic device, current news events, calendar information on the electronic device, location interests of a user of the electronic device, and content on the electronic device. In some embodiments, the receiving unit 902 is configured to receive updates to the first and second word lists at intervals of time. In some embodiments, the first and second word lists are provided by one or more applications on the electronic device. In some embodiments, a first application on the electronic device and a second application on the electronic device provide different word lists.

In some embodiments, the plurality of terms that corresponds to the communication with the other user is received (e.g., with the receiving unit 902) from a second electronic device, and the first and second word lists are based on information from the second electronic device. In some embodiments, the processing unit 904 is configured to select (e.g., with the selecting unit 910) the one or more terms in the plurality of terms by: determining (e.g., with the determining unit 908) a context associated with a first term in the plurality of terms, and selecting (e.g., with the selecting unit 910) the one or more terms based on the context associated with the first term.

In some embodiments, the receiving unit 902 is configured to receive a first plurality of terms at a first time, wherein the plurality of terms that corresponds to the communication with the other user comprises a second plurality of terms received at a second time (e.g., with the receiving unit 902), later than the first time, and the processing unit 904 is configured to select (e.g., with the selecting unit 910) the one or more terms in the second plurality of terms as the actionable terms by, in accordance with a determination (e.g., with the determining unit 908) that the second plurality of terms was received after the first plurality of terms, selecting (e.g., with the selecting unit 910) the one or more terms in the second plurality of terms as the actionable terms. In some embodiments, the processing unit 904 is configured to, in accordance with the determination that the second plurality of terms was received after the first plurality of terms, forgo selecting (e.g., with the selecting unit 910) one or more terms in the first plurality of terms as actionable terms.

In some embodiments, the processing unit 904 is configured to, in accordance with a determination that the plurality of terms includes a first term, utilizing a third word list and a fourth word list associated with the first term for selecting (e.g., with the selecting unit 910) one or more terms in the plurality of terms as actionable terms for a predetermined time period, wherein the third and fourth words lists are different from the first and the second word lists. In some embodiments, the plurality of terms is to be communicated (e.g., with the communicating unit 916) to the other user from the electronic device, and the first word list and the second word list correspond to a user of the electronic device. In some embodiments, the plurality of terms is received (e.g., with the receiving unit 902) from the other user of a second electronic device, and the first word list and the second word list correspond to the other user of the second electronic device. In some embodiments, the first word list and the second word list correspond to a user of the electronic device and the other user of a second electronic device.

In some embodiments, the current context of the plurality of terms is based on one or more of: a current application on the electronic device, a time of day, one or more recently used applications on the electronic device, a location of the electronic device, and previously received terms on the electronic device.

In accordance with some embodiments, FIG. 10 shows a functional block diagram of an electronic device 1000 configured in accordance with the principles of the various described embodiments. The functional blocks of the device are, optionally, implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described embodiments. It is understood by persons of skill in the art that the functional blocks described in FIG. 10 are, optionally, combined or separated into sub-blocks to implement the principles of the various described embodiments. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

As shown in FIG. 10, an electronic device 1000 optionally includes a receiving unit 1002 configured to receive inputs, and a processing unit 1004 coupled to the receiving unit 1002. In some embodiments, the processing unit 1004 includes an obtaining unit 1006, a display enabling unit 1008, an identifying unit 1010 and a determining unit 1012.

In some embodiments, the receiving unit 1002 is configured to receive a plurality of terms that corresponds to a communication with another user while a user interface is displayed (e.g., with the display enabling unit 1008) on a display device. In some embodiments, the processing unit 1704 is configured to: generate (e.g., with the display enabling unit 1008) a user interface for display on the display device; after receiving the plurality of terms (e.g., with the receiving unit 1002), identify (e.g., with the identifying unit 1010) one or more terms in the plurality of terms as actionable terms; obtain (e.g., with the obtaining unit 1006) related content associated with the identified one or more terms; and after obtaining the related content, concurrently display (e.g., with the display enabling unit 1008) a representation of the related content along with the received plurality of terms. In some embodiments, identifying (e.g., with the identifying unit 1010) the one or more terms in the plurality of terms as the actionable terms is based on regular expressions. In some embodiments, identifying (e.g., with the identifying unit 1010) the one or more terms in the plurality of terms as the actionable terms is based on a first word list.

In some embodiments, the plurality of terms is received (e.g., with the receiving unit 1002) from a second electronic device, and the first word list is based on information from the second electronic device. In some embodiments, the processing unit 1004 is configured to in accordance with a determination (e.g., with the determining unit 1012) that the plurality of terms includes a first term, utilizing a second word list for identifying (e.g., with the identifying unit 1010) one or more terms in the plurality of terms as actionable terms for a predetermined time period, wherein the first word list is different from the second word list.

In some embodiments, the related content is actionable. In some embodiments, the plurality of terms includes a first set of terms received (e.g., with the receiving unit 1002) at a first time and a second set of terms received (e.g., with the receiving unit 1002) at a second time that was after the first time, and identifying one or more terms in the plurality of terms as actionable terms includes comparing (e.g., with the identifying unit 1010) the first set of terms to a first word list and comparing the second set of terms to a second word list that includes more terms than the first word list.

In some embodiments, the plurality of terms includes a first set of terms received (e.g., with the receiving unit 1002) at a first time and a second set of terms received (e.g., with the receiving unit 1002) at a second time that was after the first time, and identifying one or more terms in the plurality of terms as actionable terms includes identifying (e.g., with the identifying unit 1010) one or more actionable terms in the first set of terms, and identifying (e.g., with the identifying unit 1010) one or more actionable terms in the second set of terms, and concurrently displaying (e.g., with the display enabling unit 1008) a representation of the related content along with the received plurality of terms includes displaying the related content for one or more of the actionable terms in the second set of terms without displaying related content for any of the actionable terms in the first set of terms.

In some embodiments, identifying (e.g., with the identifying unit 1010) the one or more terms in the plurality of terms comprises: determining (e.g., with the determining unit 1012) a context associated with a first term in the plurality of terms; and identifying (e.g., with the identifying unit 1010) the one or more terms based on the context associated with the first term. In some embodiments, the related content includes information about an event. In some embodiments, the related content includes transaction options for an event. In some embodiments, the identified actionable terms are visually distinguished (e.g., with the display enabling unit 1008) from other terms.

In some embodiments, the received (e.g., with the receiving unit 1002) plurality of terms includes a name of a movie, one of the actionable terms comprises the name of the movie, and the related content comprises show times for the movie at one or more theaters that are local to the electronic device. In some embodiments, the received (e.g., with the receiving unit 1002) plurality of terms includes a name of a movie, one of the actionable terms comprises the name of the movie, and the related content comprises a link to purchase one or more tickets for the movie at one or more theaters that are local to the electronic device.

The operations described above with reference to FIGS. 6A-6E and 8A-8C are, optionally, implemented by components depicted in FIGS. 1A-1B, 9 or 10. For example, receiving operations 602 and 804 are, optionally implemented by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 in event sorter 170 detects a contact on touch-sensitive display 112, and event dispatcher module 174 delivers the event information to application 136-1. A respective event recognizer 180 of application 136-1 compares the event information to respective event definitions 186, and determines whether a first contact at a first location on the touch-sensitive surface corresponds to a predefined event or sub-event, such as selection of an object on a user interface. When a respective predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally utilizes or calls data updater 176 or object updater 177 to update the application internal state 192. In some embodiments, event handler 190 accesses a respective GUI updater 178 to update what is displayed by the application. Similarly, it would be clear to a person having ordinary skill in the art how other processes can be implemented based on the components depicted in FIGS. 1A-1B, 9 or 10.

The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best use the invention and various described embodiments with various modifications as are suited to the particular use contemplated. 

1. A method comprising: at an electronic device with one or more processors and memory: receiving a plurality of terms that corresponds to a communication with another user; determining a current context of the plurality of terms; in accordance with a determination that the current context is a first context, selecting one or more terms in the plurality of terms based on a first word list as actionable terms; in accordance with a determination that the current context is a second context, different from the first context, selecting one or more terms in the plurality of terms as actionable terms based on a second word list, different from the first word list; and displaying the plurality of terms, wherein one or more of the actionable terms are visually distinguished from other terms.
 2. The method of claim 1, further comprising obtaining content associated with one or more of the actionable terms.
 3. The method of claim 2, further comprising communicating the plurality of terms and the obtained content to the other user.
 4. The method of claim 2, wherein obtaining the content comprises obtaining a link to additional content associated with one or more of the actionable terms.
 5. The method of claim 4, wherein the link comprises a link to an application on the electronic device.
 6. The method of claim 2, further comprising: prior to obtaining the content associated with the one or more of the actionable terms, receiving a selection of the one or more of the actionable terms; and in response to receiving the selection of the one or more of the actionable terms, obtaining the content associated with the selected actionable terms.
 7. The method of claim 1, wherein selection of an actionable term causes performance of an operation associated with the selected actionable term.
 8. The method of claim 7, further comprising: detecting a selection of one of the actionable terms; and in response to the selection, performing an operation associated with the selected actionable term, wherein the operation is dependent on a type of the selected actionable term.
 9. The method of claim 1, further comprising selecting one or more terms in the plurality of terms as actionable terms based on a standard word list.
 10. The method of claim 1, further comprising selecting one or more terms in the plurality of terms as actionable terms based on regular expressions.
 11. The method of claim 1, wherein the first and second contexts are based on one or more of activities of a user of the electronic device, a time of day, a currently-utilized application on the electronic device, current news events, calendar information on the electronic device, location interests of a user of the electronic device, and content on the electronic device.
 12. The method of claim 1, further comprising receiving updates to the first and second word lists at intervals of time.
 13. The method of claim 1, wherein the first and second word lists are provided by one or more applications on the electronic device.
 14. The method of claim 13, wherein a first application on the electronic device and a second application on the electronic device provide different word lists.
 15. The method of claim 1, wherein the plurality of terms that corresponds to the communication with the other user is received from a second electronic device, and the first and second word lists are based on information from the second electronic device.
 16. The method of claim 1, wherein selecting the one or more terms in the plurality of terms comprises: determining a context associated with a first term in the plurality of terms; and selecting the one or more terms based on the context associated with the first term.
 17. The method of claim 1, further comprising receiving a first plurality of terms at a first time, wherein: the plurality of terms that corresponds to the communication with the other user comprises a second plurality of terms received at a second time, later than the first time, and selecting the one or more terms in the second plurality of terms as the actionable terms comprises, in accordance with a determination that the second plurality of terms was received after the first plurality of terms, selecting the one or more terms in the second plurality of terms as the actionable terms.
 18. The method of claim 17, further comprising: in accordance with the determination that the second plurality of terms was received after the first plurality of terms, forgoing selecting one or more terms in the first plurality of terms as actionable terms.
 19. The method of claim 1, further comprising: in accordance with a determination that the plurality of terms includes a first term, utilizing a third word list and a fourth word list associated with the first term for selecting one or more terms in the plurality of terms as actionable terms for a predetermined time period, wherein the third and fourth words lists are different from the first and the second word lists.
 20. The method of claim 1, wherein: the plurality of terms is to be communicated to the other user from the electronic device, and the first word list and the second word list correspond to a user of the electronic device.
 21. The method of claim 1, wherein: the plurality of terms is received from the other user of a second electronic device, and the first word list and the second word list correspond to the other user of the second electronic device.
 22. The method of claim 1, wherein the first word list and the second word list correspond to a user of the electronic device and the other user of a second electronic device.
 23. The method of claim 1, wherein the current context of the plurality of terms is based on one or more of: a current application on the electronic device, a time of day, one or more recently used applications on the electronic device, a location of the electronic device, and previously received terms on the electronic device.
 24. An electronic device, comprising: one or more processors; memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for: receiving a plurality of terms that corresponds to a communication with another user; determining a current context of the plurality of terms; in accordance with a determination that the current context is a first context, selecting one or more terms in the plurality of terms based on a first word list as actionable terms; in accordance with a determination that the current context is a second context, different from the first context, selecting one or more terms in the plurality of terms as actionable terms based on a second word list, different from the first word list; and displaying the plurality of terms, wherein one or more of the actionable terms are visually distinguished from other terms.
 25. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by an electronic device with one or more processors and memory, cause the device to: receive a plurality of terms that corresponds to a communication with another user; determine a current context of the plurality of terms; in accordance with a determination that the current context is a first context, select one or more terms in the plurality of terms based on a first word list as actionable terms; in accordance with a determination that the current context is a second context, different from the first context, select one or more terms in the plurality of terms as actionable terms based on a second word list, different from the first word list; and display the plurality of terms, wherein one or more of the actionable terms are visually distinguished from other terms. 